Time based dispersed storage access

ABSTRACT

A method begins with a processing module receiving a data retrieval request and obtaining a real-time indicator corresponding to when the data retrieval request was received. The method continues with the processing module determining a time-based data access policy based on the data retrieval request and the real-time indicator and accessing a plurality of dispersed storage (DS) units in accordance with the time-based data access policy to retrieve encoded data slices. The method continues with the processing module decoding the threshold number of encoded data slices in accordance with an error coding dispersal storage function when a threshold number of the encoded data slices have been retrieved.

CROSS REFERENCE TO RELATED PATENTS

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. §119(e) to U.S. Provisional Application Ser. No. 61/290,757,entitled “DISTRIBUTED STORAGE TIME SYNCHRONIZATION,” (Attorney DocketNo. CS155), filed Dec. 29, 2009, pending, which is hereby incorporatedherein by reference in its entirety and made part of the present U.S.Utility patent application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

NOT APPLICABLE

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

NOT APPLICABLE

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

This invention relates generally to computing systems and moreparticularly to data storage solutions within such computing systems.

2. Description of Related Art

Computers are known to communicate, process, and store data. Suchcomputers range from wireless smart phones to data centers that supportmillions of web searches, stock trades, or on-line purchases every day.In general, a computing system generates data and/or manipulates datafrom one form into another. For instance, an image sensor of thecomputing system generates raw picture data and, using an imagecompression program (e.g., JPEG, MPEG, etc.), the computing systemmanipulates the raw picture data into a standardized compressed image.

With continued advances in processing speed and communication speed,computers are capable of processing real time multimedia data forapplications ranging from simple voice communications to streaming highdefinition video. As such, general-purpose information appliances arereplacing purpose-built communications devices (e.g., a telephone). Forexample, smart phones can support telephony communications but they arealso capable of text messaging and accessing the internet to performfunctions including email, web browsing, remote applications access, andmedia communications (e.g., telephony voice, image transfer, musicfiles, video files, real time video streaming. etc.).

Each type of computer is constructed and operates in accordance with oneor more communication, processing, and storage standards. As a result ofstandardization and with advances in technology, more and moreinformation content is being converted into digital formats. Forexample, more digital cameras are now being sold than film cameras, thusproducing more digital pictures. As another example, web-basedprogramming is becoming an alternative to over the air televisionbroadcasts and/or cable broadcasts. As further examples, papers, books,video entertainment, home video, etc. are now being stored digitally,which increases the demand on the storage function of computers.

A typical computer storage system includes one or more memory devicesaligned with the needs of the various operational aspects of thecomputer's processing and communication functions. Generally, theimmediacy of access dictates what type of memory device is used. Forexample, random access memory (RAM) memory can be accessed in any randomorder with a constant response time, thus it is typically used for cachememory and main memory. By contrast, memory device technologies thatrequire physical movement such as magnetic disks, tapes, and opticaldiscs, have a variable response time as the physical movement can takelonger than the data transfer, thus they are typically used forsecondary memory (e.g., hard drive, backup memory, etc.).

A computer's storage system will be compliant with one or more computerstorage standards that include, but are not limited to, network filesystem (NFS), flash file system (FFS), disk file system (DFS), smallcomputer system interface (SCSI), internet small computer systeminterface (iSCSI), file transfer protocol (FTP), and web-baseddistributed authoring and versioning (WebDAV). These standards specifythe data storage format (e.g., files, data objects, data blocks,directories, etc.) and interfacing between the computer's processingfunction and its storage system, which is a primary function of thecomputer's memory controller.

Despite the standardization of the computer and its storage system,memory devices fail; especially commercial grade memory devices thatutilize technologies incorporating physical movement (e.g., a discdrive). For example, it is fairly common for a disc drive to routinelysuffer from bit level corruption and to completely fail after threeyears of use. One solution is to a higher-grade disc drive, which addssignificant cost to a computer.

Another solution is to utilize multiple levels of redundant disc drivesto replicate the data into two or more copies. One such redundant driveapproach is called redundant array of independent discs (RAID). In aRAID device, a RAID controller adds parity data to the original databefore storing it across the array. The parity data is calculated fromthe original data such that the failure of a disc will not result in theloss of the original data. For example, RAID 5 uses three discs toprotect data from the failure of a single disc. The parity data, andassociated redundancy overhead data, reduces the storage capacity ofthree independent discs by one third (e.g., n−1=capacity). RAID 6 canrecover from a loss of two discs and requires a minimum of four discswith a storage capacity of n−2.

While RAID addresses the memory device failure issue, it is not withoutits own failures issues that affect its effectiveness, efficiency andsecurity. For instance, as more discs are added to the array, theprobability of a disc failure increases, which increases the demand formaintenance. For example, when a disc fails, it needs to be manuallyreplaced before another disc fails and the data stored in the RAIDdevice is lost. To reduce the risk of data loss, data on a RAID deviceis typically copied on to one or more other RAID devices. While thisaddresses the loss of data issue, it raises a security issue sincemultiple copies of data are available, which increases the chances ofunauthorized access. Further, as the amount of data being stored grows,the overhead of RAID devices becomes a non-trivial efficiency issue.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a computingsystem in accordance with the invention;

FIG. 2 is a schematic block diagram of an embodiment of a computing corein accordance with the invention;

FIG. 3 is a schematic block diagram of an embodiment of a distributedstorage processing unit in accordance with the invention;

FIG. 4 is a schematic block diagram of an embodiment of a grid module inaccordance with the invention;

FIG. 5 is a diagram of an example embodiment of error coded data slicecreation in accordance with the invention;

FIG. 6 is a flowchart illustrating an example of storing encoded dataslices in accordance with the invention;

FIG. 7 is a flowchart illustrating an example of retrieving encoded dataslices in accordance with the invention;

FIG. 8 is a flowchart illustrating an example of deleting encoded dataslices in accordance with the invention;

FIG. 9 is a flowchart illustrating an example of updating an accesspolicy in accordance with the invention;

FIGS. 10A-10C are schematic block diagrams of embodiments of a dispersedstorage network (DSN) memory storage set in accordance with theinvention;

FIG. 11 is another flowchart illustrating another example of updating anaccess policy in accordance with the invention;

FIG. 12 is a flowchart illustrating an example of retrieving a dataobject in accordance with the invention;

FIG. 13 is a schematic block diagram of another embodiment of acomputing system in accordance with the invention;

FIG. 14 is a timing diagram of an example storage sequence in accordancewith the invention;

FIG. 15 is a timing diagram of an example retrieval sequence inaccordance with the invention;

FIG. 16 is a flowchart illustrating an example of storing a data objectin accordance with the invention;

FIG. 17 is another flowchart illustrating another example of retrievingencoded data slices in accordance with the invention;

FIG. 18 is a schematic block diagram of another embodiment of acomputing system in accordance with the invention;

FIG. 19 is another timing diagram of another example storage sequence inaccordance with the invention; and

FIG. 20 is a flowchart illustrating an example of outputting slices inaccordance with the invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of a computing system 10 thatincludes one or more of a first type of user devices 12, one or more ofa second type of user devices 14, at least one distributed storage (DS)processing unit 16, at least one DS managing unit 18, at least onestorage integrity processing unit 20, and a distributed storage network(DSN) memory 22 coupled via a network 24. The network 24 may include oneor more wireless and/or wire lined communication systems; one or moreprivate intranet systems and/or public internet systems; and/or one ormore local area networks (LAN) and/or wide area networks (WAN).

The DSN memory 22 includes a plurality of distributed storage (DS) units36 for storing data of the system. Each of the DS units 36 includes aprocessing module and memory and may be located at a geographicallydifferent site than the other DS units (e.g., one in Chicago, one inMilwaukee, etc.). The processing module may be a single processingdevice or a plurality of processing devices. Such a processing devicemay be a microprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, field programmable gate array,programmable logic device, state machine, logic circuitry, analogcircuitry, digital circuitry, and/or any device that manipulates signals(analog and/or digital) based on hard coding of the circuitry and/oroperational instructions. The processing module may have an associatedmemory and/or memory element, which may be a single memory device, aplurality of memory devices, and/or embedded circuitry of the processingmodule. Such a memory device may be a read-only memory, random accessmemory, volatile memory, non-volatile memory, static memory, dynamicmemory, flash memory, cache memory, and/or any device that storesdigital information. Note that if the processing module includes morethan one processing device, the processing devices may be centrallylocated (e.g., directly coupled together via a wired and/or wireless busstructure) or may be distributedly located (e.g., cloud computing viaindirect coupling via a local area network and/or a wide area network).Further note that when the processing module implements one or more ofits functions via a state machine, analog circuitry, digital circuitry,and/or logic circuitry, the memory and/or memory element storing thecorresponding operational instructions may be embedded within, orexternal to, the circuitry comprising the state machine, analogcircuitry, digital circuitry, and/or logic circuitry. Still further notethat, the memory element stores, and the processing module executes,hard coded and/or operational instructions corresponding to at leastsome of the steps and/or functions illustrated in FIGS. 1-20.

Each of the user devices 12-14, the DS processing unit 16, the DSmanaging unit 18, and the storage integrity processing unit 20 may be aportable computing device (e.g., a social networking device, a gamingdevice, a cell phone, a smart phone, a personal digital assistant, adigital music player, a digital video player, a laptop computer, ahandheld computer, a video game controller, and/or any other portabledevice that includes a computing core) and/or a fixed computing device(e.g., a personal computer, a computer server, a cable set-top box, asatellite receiver, a television set, a printer, a fax machine, homeentertainment equipment, a video game console, and/or any type of homeor office computing equipment). Such a portable or fixed computingdevice includes a computing core 26 and one or more interfaces 30, 32,and/or 33. An embodiment of the computing core 26 will be described withreference to FIG. 2.

With respect to the interfaces, each of the interfaces 30, 32, and 33includes software and/or hardware to support one or more communicationlinks via the network 24 and/or directly. For example, interfaces 30support a communication link (wired, wireless, direct, via a LAN, viathe network 24, etc.) between the first type of user device 14 and theDS processing unit 16. As another example, DSN interface 32 supports aplurality of communication links via the network 24 between the DSNmemory 22 and the DS processing unit 16, the first type of user device12, and/or the storage integrity processing unit 20. As yet anotherexample, interface 33 supports a communication link between the DSmanaging unit 18 and any one of the other devices and/or units 12, 14,16, 20, and/or 22 via the network 24.

In general and with respect to data storage, the system 10 supportsthree primary functions: distributed network data storage management,distributed data storage and retrieval, and data storage integrityverification. In accordance with these three primary functions, data canbe distributedly stored in a plurality of physically different locationsand subsequently retrieved in a reliable and secure manner regardless offailures of individual storage devices, failures of network equipment,the duration of storage, the amount of data being stored, attempts athacking the data, etc.

The DS managing unit 18 performs distributed network data storagemanagement functions, which include establishing distributed datastorage parameters, performing network operations, performing networkadministration, and/or performing network maintenance. The DS managingunit 18 establishes the distributed data storage parameters (e.g.,allocation of virtual DSN memory space, distributed storage parameters,security parameters, billing information, user profile information,etc.) for one or more of the user devices 12-14 (e.g., established forindividual devices, established for a user group of devices, establishedfor public access by the user devices, etc.). For example, the DSmanaging unit 18 coordinates the creation of a vault (e.g., a virtualmemory block) within the DSN memory 22 for a user device (for a group ofdevices, or for public access). The DS managing unit 18 also determinesthe distributed data storage parameters for the vault. In particular,the DS managing unit 18 determines a number of slices (e.g., the numberthat a data segment of a data file and/or data block is partitioned intofor distributed storage) and a read threshold value (e.g., the minimumnumber of slices required to reconstruct the data segment).

As another example, the DS managing module 18 creates and stores,locally or within the DSN memory 22, user profile information. The userprofile information includes one or more of authentication information,permissions, and/or the security parameters. The security parameters mayinclude one or more of encryption/decryption scheme, one or moreencryption keys, key generation scheme, and data encoding/decodingscheme.

As yet another example, the DS managing unit 18 creates billinginformation for a particular user, user group, vault access, publicvault access, etc. For instance, the DS managing unit 18 tracks thenumber of times user accesses a private vault and/or public vaults,which can be used to generate a per-access bill. In another instance,the DS managing unit 18 tracks the amount of data stored and/orretrieved by a user device and/or a user group, which can be used togenerate a per-data-amount bill.

The DS managing unit 18 also performs network operations, networkadministration, and/or network maintenance. As at least part ofperforming the network operations and/or administration, the DS managingunit 18 monitors performance of the devices and/or units of the system10 for potential failures, determines the devices and/or unit'sactivation status, determines the devices' and/or units' loading, andany other system level operation that affects the performance level ofthe system 10. For example, the DS managing unit 18 receives andaggregates network management alarms, alerts, errors, statusinformation, performance information, and messages from the devices12-14 and/or the units 16, 20, 22. For example, the DS managing unit 18receives a simple network management protocol (SNMP) message regardingthe status of the DS processing unit 16.

The DS managing unit 18 performs the network maintenance by identifyingequipment within the system 10 that needs replacing, upgrading,repairing, and/or expanding. For example, the DS managing unit 18determines that the DSN memory 22 needs more DS units 36 or that one ormore of the DS units 36 needs updating.

The second primary function (i.e., distributed data storage andretrieval) begins and ends with a user device 12-14. For instance, if asecond type of user device 14 has a data file 38 and/or data block 40 tostore in the DSN memory 22, it send the data file 38 and/or data block40 to the DS processing unit 16 via its interface 30. As will bedescribed in greater detail with reference to FIG. 2, the interface 30functions to mimic a conventional operating system (OS) file systeminterface (e.g., network file system (NFS), flash file system (FFS),disk file system (DFS), file transfer protocol (FTP), web-baseddistributed authoring and versioning (WebDAV), etc.) and/or a blockmemory interface (e.g., small computer system interface (SCSI), internetsmall computer system interface (iSCSI), etc.). In addition, theinterface 30 may attach a user identification code (ID) to the data file38 and/or data block 40.

The DS processing unit 16 receives the data file 38 and/or data block 40via its interface 30 and performs a distributed storage (DS) process 34thereon (e.g., an error coding dispersal storage function). The DSprocessing 34 begins by partitioning the data file 38 and/or data block40 into one or more data segments, which is represented as Y datasegments. For example, the DS processing 34 may partition the data file38 and/or data block 40 into a fixed byte size segment (e.g., 2¹ to2^(n) bytes, where n=>2) or a variable byte size (e.g., change byte sizefrom segment to segment, or from groups of segments to groups ofsegments, etc.).

For each of the Y data segments, the DS processing 34 error encodes(e.g., forward error correction (FEC), information dispersal algorithm,or error correction coding) and slices (or slices then error encodes)the data segment into a plurality of error coded (EC) data slices 42-48,which is represented as X slices per data segment. The number of slices(X) per segment, which corresponds to a number of pillars n, is set inaccordance with the distributed data storage parameters and the errorcoding scheme. For example, if a Reed-Solomon (or other FEC scheme) isused in an n/k system, then a data segment is divided into n slices,where k number of slices is needed to reconstruct the original data(i.e., k is the threshold). As a few specific examples, the n/k factormay be 5/3; 6/4; 8/6; 8/5; 16/10.

For each slice 42-48, the DS processing unit 16 creates a unique slicename and appends it to the corresponding slice 42-48. The slice nameincludes universal DSN memory addressing routing information (e.g.,virtual memory addresses in the DSN memory 22) and user-specificinformation (e.g., user ID, file name, data block identifier, etc.).

The DS processing unit 16 transmits the plurality of EC slices 42-48 toa plurality of DS units 36 of the DSN memory 22 via the DSN interface 32and the network 24. The DSN interface 32 formats each of the slices fortransmission via the network 24. For example, the DSN interface 32 mayutilize an internet protocol (e.g., TCP/IP, etc.) to packetize theslices 42-48 for transmission via the network 24.

The number of DS units 36 receiving the slices 42-48 is dependent on thedistributed data storage parameters established by the DS managing unit18. For example, the DS managing unit 18 may indicate that each slice isto be stored in a different DS unit 36. As another example, the DSmanaging unit 18 may indicate that like slice numbers of different datasegments are to be stored in the same DS unit 36. For example, the firstslice of each of the data segments is to be stored in a first DS unit36, the second slice of each of the data segments is to be stored in asecond DS unit 36, etc. In this manner, the data is encoded anddistributedly stored at physically diverse locations to improved datastorage integrity and security. Further examples of encoding the datasegments will be provided with reference to one or more of FIGS. 2-20.

Each DS unit 36 that receives a slice 42-48 for storage translates thevirtual DSN memory address of the slice into a local physical addressfor storage. Accordingly, each DS unit 36 maintains a virtual tophysical memory mapping to assist in the storage and retrieval of data.

The first type of user device 12 performs a similar function to storedata in the DSN memory 22 with the exception that it includes the DSprocessing. As such, the device 12 encodes and slices the data fileand/or data block it has to store. The device then transmits the slices11 to the DSN memory via its DSN interface 32 and the network 24.

For a second type of user device 14 to retrieve a data file or datablock from memory, it issues a read command via its interface 30 to theDS processing unit 16. The DS processing unit 16 performs the DSprocessing 34 to identify the DS units 36 storing the slices of the datafile and/or data block based on the read command. The DS processing unit16 may also communicate with the DS managing unit 18 to verify that theuser device 14 is authorized to access the requested data.

Assuming that the user device is authorized to access the requesteddata, the DS processing unit 16 issues slice read commands to at least athreshold number of the DS units 36 storing the requested data (e.g., toat least 10 DS units for a 16/10 error coding scheme). Each of the DSunits 36 receiving the slice read command, verifies the command,accesses its virtual to physical memory mapping, retrieves the requestedslice, or slices, and transmits it to the DS processing unit 16.

Once the DS processing unit 16 has received a read threshold number ofslices for a data segment, it performs an error decoding function andde-slicing to reconstruct the data segment. When Y number of datasegments has been reconstructed, the DS processing unit 16 provides thedata file 38 and/or data block 40 to the user device 14. Note that thefirst type of user device 12 performs a similar process to retrieve adata file and/or data block.

The storage integrity processing unit 20 performs the third primaryfunction of data storage integrity verification. In general, the storageintegrity processing unit 20 periodically retrieves slices 45, and/orslice names, of a data file or data block of a user device to verifythat one or more slices have not been corrupted or lost (e.g., the DSunit failed). The retrieval process mimics the read process previouslydescribed.

If the storage integrity processing unit 20 determines that one or moreslices is corrupted or lost, it rebuilds the corrupted or lost slice(s)in accordance with the error coding scheme. The storage integrityprocessing unit 20 stores the rebuild slice, or slices, in theappropriate DS unit(s) 36 in a manner that mimics the write processpreviously described.

FIG. 2 is a schematic block diagram of an embodiment of a computing core26 that includes a processing module 50, a memory controller 52, mainmemory 54, a video graphics processing unit 55, an input/output (IO)controller 56, a peripheral component interconnect (PCI) interface 58,at least one IO device interface module 62, a read only memory (ROM)basic input output system (BIOS) 64, and one or more memory interfacemodules. The memory interface module(s) includes one or more of auniversal serial bus (USB) interface module 66, a host bus adapter (HBA)interface module 68, a network interface module 70, a flash interfacemodule 72, a hard drive interface module 74, and a DSN interface module76. Note the DSN interface module 76 and/or the network interface module70 may function as the interface 30 of the user device 14 of FIG. 1.Further note that the IO device interface module 62 and/or the memoryinterface modules may be collectively or individually referred to as IOports.

The processing module 50 may be a single processing device or aplurality of processing devices. Such a processing device may be amicroprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, field programmable gate array,programmable logic device, state machine, logic circuitry, analogcircuitry, digital circuitry, and/or any device that manipulates signals(analog and/or digital) based on hard coding of the circuitry and/oroperational instructions. The processing module 50 may have anassociated memory and/or memory element, which may be a single memorydevice, a plurality of memory devices, and/or embedded circuitry of theprocessing module 50. Such a memory device may be a read-only memory,random access memory, volatile memory, non-volatile memory, staticmemory, dynamic memory, flash memory, cache memory, and/or any devicethat stores digital information. Note that if the processing module 50includes more than one processing device, the processing devices may becentrally located (e.g., directly coupled together via a wired and/orwireless bus structure) or may be distributedly located (e.g., cloudcomputing via indirect coupling via a local area network and/or a widearea network). Further note that when the processing module 50implements one or more of its functions via a state machine, analogcircuitry, digital circuitry, and/or logic circuitry, the memory and/ormemory element storing the corresponding operational instructions may beembedded within, or external to, the circuitry comprising the statemachine, analog circuitry, digital circuitry, and/or logic circuitry.Still further note that, the memory element stores, and the processingmodule 50 executes, hard coded and/or operational instructionscorresponding to at least some of the steps and/or functions illustratedin FIGS. 1-20.

FIG. 3 is a schematic block diagram of an embodiment of a dispersedstorage (DS) processing module 34 of user device 12 and/or of the DSprocessing unit 16. The DS processing module 34 includes a gatewaymodule 78, an access module 80, a grid module 82, and a storage module84. The DS processing module 34 may also include an interface 30 and theDSnet interface 32 or the interfaces 68 and/or 70 may be part of user 12or of the DS processing unit 14. The DS processing module 34 may furtherinclude a bypass/feedback path between the storage module 84 to thegateway module 78. Note that the modules 78-84 of the DS processingmodule 34 may be in a single unit or distributed across multiple units.

In an example of storing data, the gateway module 78 receives anincoming data object that includes a user ID field 86, an object namefield 88, and the data field 40 and may also receive correspondinginformation that includes a process identifier (e.g., an internalprocess/application ID), metadata, a file system directory, a blocknumber, a transaction message, a user device identity (ID), a dataobject identifier, a source name, and/or user information. The gatewaymodule 78 authenticates the user associated with the data object byverifying the user ID 86 with the managing unit 18 and/or anotherauthenticating unit.

When the user is authenticated, the gateway module 78 obtains userinformation from the management unit 18, the user device, and/or theother authenticating unit. The user information includes a vaultidentifier, operational parameters, and user attributes (e.g., userdata, billing information, etc.). A vault identifier identifies a vault,which is a virtual memory space that maps to a set of DS storage units36. For example, vault 1 (i.e., user 1's DSN memory space) includeseight DS storage units (X=8 wide) and vault 2 (i.e., user 2's DSN memoryspace) includes sixteen DS storage units (X=16 wide). The operationalparameters may include an error coding algorithm, the width n (number ofpillars X or slices per segment for this vault), a read threshold T, awrite threshold, an encryption algorithm, a slicing parameter, acompression algorithm, an integrity check method, caching settings,parallelism settings, and/or other parameters that may be used to accessthe DSN memory layer.

The gateway module 78 uses the user information to assign a source name35 to the data. For instance, the gateway module 60 determines thesource name 35 of the data object 40 based on the vault identifier andthe data object. For example, the source name may contain a fileidentifier (ID), a vault generation number, a reserved field, and avault identifier (ID). As another example, the gateway module 78 maygenerate the file ID based on a hash function of the data object 40.Note that the gateway module 78 may also perform message conversion,protocol conversion, electrical conversion, optical conversion, accesscontrol, user identification, user information retrieval, trafficmonitoring, statistics generation, configuration, management, and/orsource name determination.

The access module 80 receives the data object 40 and creates a series ofdata segments 1 through Y 90-92 in accordance with a data storageprotocol (e.g., file storage system, a block storage system, and/or anaggregated block storage system). The number of segments Y may be chosenor randomly assigned based on a selected segment size and the size ofthe data object. For example, if the number of segments is chosen to bea fixed number, then the size of the segments varies as a function ofthe size of the data object. For instance, if the data object is animage file of 4,194,304 eight bit bytes (e.g., 33,554,432 bits) and thenumber of segments Y=131,072, then each segment is 256 bits or 32 bytes.As another example, if segment sized is fixed, then the number ofsegments Y varies based on the size of data object. For instance, if thedata object is an image file of 4,194,304 bytes and the fixed size ofeach segment is 4,096 bytes, the then number of segments Y=1,024. Notethat each segment is associated with the same source name.

The grid module 82 receives the data segments and may manipulate (e.g.,compression, encryption, cyclic redundancy check (CRC), etc.) each ofthe data segments before performing an error coding function of theerror coding dispersal storage function to produce a pre-manipulateddata segment. After manipulating a data segment, if applicable, the gridmodule 82 error encodes (e.g., Reed-Solomon, Convolution encoding,Trellis encoding, etc.) the data segment or manipulated data segmentinto X error coded data slices 42-44.

The value X, or the number of pillars (e.g., X=16), is chosen as aparameter of the error coding dispersal storage function. Otherparameters of the error coding dispersal function include a readthreshold T, a write threshold W, etc. The read threshold (e.g., T=10,when X=16) corresponds to the minimum number of error-free error codeddata slices required to reconstruct the data segment. In other words,the DS processing module 34 can compensate for X−T (e.g., 16−10=6)missing error coded data slices per data segment. The write threshold Wcorresponds to a minimum number of DS storage units that acknowledgeproper storage of their respective data slices before the DS processingmodule indicates proper storage of the encoded data segment. Note thatthe write threshold is greater than or equal to the read threshold for agiven number of pillars (X).

For each data slice of a data segment, the grid module 82 generates aunique slice name 37 and attaches it thereto. The slice name 37 includesa universal routing information field and a vault specific field and maybe 48 bytes (e.g., 24 bytes for each of the universal routinginformation field and the vault specific field). As illustrated, theuniversal routing information field includes a slice index, a vault ID,a vault generation, and a reserved field. The slice index is based onthe pillar number and the vault ID and, as such, is unique for eachpillar (e.g., slices of the same pillar for the same vault for anysegment will share the same slice index). The vault specific fieldincludes a data name, which includes a file ID and a segment number(e.g., a sequential numbering of data segments 1-Y of a simple dataobject or a data block number).

Prior to outputting the error coded data slices of a data segment, thegrid module may perform post-slice manipulation on the slices. Ifenabled, the manipulation includes slice level compression, encryption,CRC, addressing, tagging, and/or other manipulation to improve theeffectiveness of the computing system.

When the error coded data slices of a data segment are ready to beoutputted, the grid module 82 determines which of the DS storage units36 will store the EC data slices based on a dispersed storage memorymapping associated with the user's vault and/or DS storage unitattributes. The DS storage unit attributes may include availability,self-selection, performance history, link speed, link latency,ownership, available DSN memory, domain, cost, a prioritization scheme,a centralized selection message from another source, a lookup table,data ownership, and/or any other factor to optimize the operation of thecomputing system. Note that the number of DS storage units 36 is equalto or greater than the number of pillars (e.g., X) so that no more thanone error coded data slice of the same data segment is stored on thesame DS storage unit 36. Further note that EC data slices of the samepillar number but of different segments (e.g., EC data slice 1 of datasegment 1 and EC data slice 1 of data segment 2) may be stored on thesame or different DS storage units 36.

The storage module 84 performs an integrity check on the outboundencoded data slices and, when successful, identifies a plurality of DSstorage units based on information provided by the grid module 82. Thestorage module 84 then outputs the encoded data slices 1 through X ofeach segment 1 through Y to the DS storage units 36. Each of the DSstorage units 36 stores its EC data slice(s) and maintains a localvirtual DSN address to physical location table to convert the virtualDSN address of the EC data slice(s) into physical storage addresses.

In an example of a read operation, the user device 12 and/or 14 sends aread request to the DS processing unit 14, which authenticates therequest. When the request is authentic, the DS processing unit 14 sendsa read message to each of the DS storage units 36 storing slices of thedata object being read. The slices are received via the DSnet interface32 and processed by the storage module 84, which performs a parity checkand provides the slices to the grid module 82 when the parity check wassuccessful. The grid module 82 decodes the slices in accordance with theerror coding dispersal storage function to reconstruct the data segment.The access module 80 reconstructs the data object from the data segmentsand the gateway module 78 formats the data object for transmission tothe user device.

FIG. 4 is a schematic block diagram of an embodiment of a grid module 82that includes a control unit 73, a pre-slice manipulator 75, an encoder77, a slicer 79, a post-slice manipulator 81, a pre-slice de-manipulator83, a decoder 85, a de-slicer 87, and/or a post-slice de-manipulator 89.Note that the control unit 73 may be partially or completely external tothe grid module 82. For example, the control unit 73 may be part of thecomputing core at a remote location, part of a user device, part of theDS managing unit 18, or distributed amongst one or more DS storageunits.

In an example of write operation, the pre-slice manipulator 75 receivesa data segment 90-92 and a write instruction from an authorized userdevice. The pre-slice manipulator 75 determines if pre-manipulation ofthe data segment 90-92 is required and, if so, what type. The pre-slicemanipulator 75 may make the determination independently or based oninstructions from the control unit 73, where the determination is basedon a computing system-wide predetermination, a table lookup, vaultparameters associated with the user identification, the type of data,security requirements, available DSN memory, performance requirements,and/or other metadata.

Once a positive determination is made, the pre-slice manipulator 75manipulates the data segment 90-92 in accordance with the type ofmanipulation. For example, the type of manipulation may be compression(e.g., Lempel-Ziv-Welch, Huffman, Golomb, fractal, wavelet, etc.),signatures (e.g., Digital Signature Algorithm (DSA), Elliptic Curve DSA,Secure Hash Algorithm, etc.), watermarking, tagging, encryption (e.g.,Data Encryption Standard, Advanced Encryption Standard, etc.), addingmetadata (e.g., time/date stamping, user information, file type, etc.),cyclic redundancy check (e.g., CRC32), and/or other data manipulationsto produce the pre-manipulated data segment.

The encoder 77 encodes the pre-manipulated data segment 92 using aforward error correction (FEC) encoder (and/or other type of erasurecoding and/or error coding) to produce an encoded data segment 94. Theencoder 77 determines which forward error correction algorithm to usebased on a predetermination associated with the user's vault, a timebased algorithm, user direction, DS managing unit direction, controlunit direction, as a function of the data type, as a function of thedata segment 92 metadata, and/or any other factor to determine algorithmtype. The forward error correction algorithm may be Golay,Multidimensional parity, Reed-Solomon, Hamming, Bose Ray ChauduriHocquenghem (BCH), Cauchy-Reed-Solomon, or any other FEC encoder. Notethat the encoder 77 may use a different encoding algorithm for each datasegment 92, the same encoding algorithm for the data segments 92 of adata object, or a combination thereof.

The encoded data segment 94 is of greater size than the data segment 92by the overhead rate of the encoding algorithm by a factor of X/T, whereX is the width or number of slices, and T is the read threshold. In thisregard, the corresponding decoding process can accommodate at most X−Tmissing EC data slices and still recreate the data segment 92. Forexample, if X=16 and T=10, then the data segment 92 will be recoverableas long as 10 or more EC data slices per segment are not corrupted.

The slicer 79 transforms the encoded data segment 94 into EC data slicesin accordance with the slicing parameter from the vault for this userand/or data segment 92. For example, if the slicing parameter is X=16,then the slicer 79 slices each encoded data segment 94 into 16 encodedslices.

The post-slice manipulator 81 performs, if enabled, post-manipulation onthe encoded slices to produce the EC data slices. If enabled, thepost-slice manipulator 81 determines the type of post-manipulation,which may be based on a computing system-wide predetermination,parameters in the vault for this user, a table lookup, the useridentification, the type of data, security requirements, available DSNmemory, performance requirements, control unit directed, and/or othermetadata. Note that the type of post-slice manipulation may includeslice level compression, signatures, encryption, CRC, addressing,watermarking, tagging, adding metadata, and/or other manipulation toimprove the effectiveness of the computing system.

In an example of a read operation, the post-slice de-manipulator 89receives at least a read threshold number of EC data slices and performsthe inverse function of the post-slice manipulator 81 to produce aplurality of encoded slices. The de-slicer 87 de-slices the encodedslices to produce an encoded data segment 94. The decoder 85 performsthe inverse function of the encoder 77 to recapture the data segment90-92. The pre-slice de-manipulator 83 performs the inverse function ofthe pre-slice manipulator 75 to recapture the data segment 90-92.

FIG. 5 is a diagram of an example of slicing an encoded data segment 94by the slicer 79. In this example, the encoded data segment 94 includesthirty-two bits, but may include more or less bits. The slicer 79disperses the bits of the encoded data segment 94 across the EC dataslices in a pattern as shown. As such, each EC data slice does notinclude consecutive bits of the data segment 94 reducing the impact ofconsecutive bit failures on data recovery. For example, if EC data slice2 (which includes bits 1, 5, 9, 13, 17, 25, and 29) is unavailable(e.g., lost, inaccessible, or corrupted), the data segment can bereconstructed from the other EC data slices (e.g., 1, 3 and 4 for a readthreshold of 3 and a width of 4).

FIG. 6 is a flowchart illustrating an example of storing encoded dataslices. The method begins at step 102 where a processing module (e.g.,of a dispersed storage (DS) unit) receives slice(s), slice names, and/oran access policy from any one of a user device, a DS processing unit, astorage integrity processing unit, a DS managing unit, and another DSunit. The access policy may include a time varying availability patternof a DS unit, a pillar, and/or a vault. For example, the patternindicates that vault 1 is available to any user from noon to midnightevery day and is not available from midnight to noon. In anotherexample, the pattern indicates that pillar 2 of vault 3 is available toany user from noon to midnight every day and is not available frommidnight to noon. In another example, the pattern indicates that pillar2 of vault 3 is available only to user 5 from noon to midnight every dayand is available to the DS managing unit 24 hours a day. Note that theaccess policy may be previously determined by any one or more of theuser device, the DS processing unit, the storage integrity processingunit, the DS managing unit, and another DS unit. The access policydetermination is discussed in greater detail with reference to FIGS.9-11.

At step 104, the processing module determines a current timestamp basedon a time function of an associated computing core 26 or of thecomputing system. For example, when the slices and/or the access policyare received, the processing module determines a current time (e.g.,10:14:53 AM GMT) from a shared clock source (e.g., Unix time clock,POSIX time clock, etc.) and uses the current time for the timestamp. Atstep 106, the processing module coordinates storage of the slices, slicenames, access policy, and timestamp in a memory (e.g., a local memoryassociated with a DS unit). In an example, the processing module storesthe slices in a main slice memory and the slice names, access policy,and timestamp in a local virtual DSN address to physical location tablerecord such that each is linked to the other for subsequent simultaneousretrieval.

FIG. 7 is a flowchart illustrating an example of retrieving encoded dataslices. The method begins with step 108 where the processing module(e.g., of a dispersed storage (DS) unit) receives a slice retrievalrequest from a requester, which may be a user device, a DS processingunit, a storage integrity processing unit, a DS managing unit, and/oranother DS unit. The request may include one or more of a slice name(s),a requester ID, a command, an access policy update, a data object ID, asource name, a data type, a data size indicator, a priority indicator, asecurity indicator, and a performance indicator.

At step 110, the processing module determines an access policy to applyto the retrieval request based on one or more of a lookup in memory of apreviously received access policy, the slice name(s), the requester ID,a command, an access policy update, a data object ID, a source name, adata type, a data size indicator, a priority indicator, a securityindicator, and performance indicator. For example, the processing moduledetermines the access policy based on the stored access policyassociated with the slice names.

At step 112, the processing module determines a timestamp for thereceiving of the request. At step 114, the processing module determinesif slice(s) are available based on one or more of the access policy, thetimestamp, a memory status indicator, a DS unit status indicator, and aperformance indicator. In an example, the processing module determinesthat the slices are currently unavailable when the access policy patternindicates that no user and/or unit currently has access authorization.In another example, the processing module determines that the slices arecurrently available when the access policy pattern indicates that atleast one user and/or at least one unit currently has accessauthorization. The method branches to step 118 when the processingmodule determines that slice(s) are available. The method ends with step116 when the DS unit determines that slice(s) are not available. At step116, the processing module sends an unavailable message to the requestersuch that the requester may try again later or give up.

At step 118, the processing module determines if slice(s) are availableto the requester. Such a determination based may be based on one or moreof the access policy, the timestamp, a memory status indicator, a DSunit status indicator, and a performance indicator. For example, theprocessing module determines that the slices are available to therequester when the user ID associated with the requester is listed inthe access policy pattern for the current timestamp. The method branchesto step 122 when the processing module determines that the slice(s) arenot available to the requester. The method continues to step 120 whenthe processing module determines that slice(s) are available. At step120, the processing module retrieves the slice(s) from memory and sendsthe slice(s) to the requester. At step 122, the processing module sendsan unavailable message to the requester when the DS unit determines thatthe slice(s) are not available to the requester.

FIG. 8 is a flowchart illustrating an example of deleting encoded dataslices. The method begins at step 124 where a processing module (e.g.,of one of a DS unit, a DS processing unit, a storage integrityprocessing unit, the DS managing unit and/or a user device) determinesone or more slice names of slices to consider for deletion. Note thatthe one or more slice names may include discrete and non-contiguousslice names and/or a contiguous range (e.g., that are associated withthe same data segment and/or same data object). Such a determination maybe based on one or more of where a deletion process left off last time,a starting DSN address, a lookup, a command, a request, a random number,a vault ID, a data object ID, and a local virtual DSN address tophysical location table.

At step 126, the processing module determines an access policy (e.g.,who can access the slice and/or when) based on one or more of a storedaccess policy for the slice names (e.g., the policy saved when the slicewas saved in the DS unit memory), a command, a request, apredetermination, and a DS managing unit message. At step 128, theprocessing module determines the current timestamp.

At step 130, the processing module determines slice availability (e.g.,will the slice(s) ever be available again, now, or in the future) basedon one or more of the access policy, the timestamp, a command, arequest, a predetermination, the requester, and a DS managing unitmessage. In an example, the processing module determines that theslice(s) will be available sometime when the access policy indicatesthat the slice(s) are available to the DS managing unit a month from thepresent time. If this is the case, the method repeats at step 124.

If, however, the processing module determines that the slice(s) will benever again be available for a particular user (or set of users) basedon the access policy indicating that the slice(s) are no longeravailable to the user device(s), the method continues at step 132. Atstep 132, the processing module determines if reconsideration ofavailability to the user (or set of users) is desired. For instance, theprocessing module determines whether a potential access policy change iscontemplated and/or implemented. Such a determination may be based onone or more of the current access policy, a reconsideration time window,a user device ID, a vault lookup, a command, a predetermination, a DSmanaging unit message, and the current timestamp. In an example, theprocessing module determines to reconsider when the access policyindicates that a reconsideration may be requested within seven days ofthe last time the slice transitioned from available to unavailable andthat transition occurred two days ago. In another example, theprocessing module determines to not reconsider when the access policyindicates that reconsideration may never be requested. Ifreconsideration is denied, the method continues to step 136 where theprocessing module deletes the slice(s) from the memory or moves theslices to an archive storage that is not accessible to the user (or setof users).

If reconsideration is determined, the method continues at step 134 wherethe processing module sends, via an interface, a reconsideration requestmessage to one or more of the DS unit, the DS processing, the storageintegrity processing unit, the DS managing unit, and the user device.The message may include any one or more of the DS unit ID, the slicename(s), a command, and the access policy. In response, the processingmodule may subsequently receive a reconsideration request responsemessage that includes either a denial message or a new access policy.The processing module saves the new access policy and utilizes the newaccess policy for the slice(s) when the reconsideration request responsemessage contains a new access policy.

FIG. 9 is a flowchart illustrating an example of updating an accesspolicy. The method begins with step 138 where a processing module (e.g.,of one of a DS processing unit, a DS unit, a storage integrityprocessing unit, a DS managing unit and/or a user device) determines oneor more slice names of slices to consider for an access policy update.Note that the one or more slice names may include discrete andnon-contiguous slice names and/or a contiguous range (e.g., that areassociated with the same data segment and/or same data object). Such adetermination may be based on one or more of an access policyreconsideration request, where a process left off last time, a startingDSN address, a lookup, a command, a request, a random number, a vaultID, a data object ID, and/or a virtual DSN address to physical locationtable.

At step 140, the processing module determines whether to establish a newaccess policy (e.g., who can access the slice and/or when the slices canbe accessed) based on one or more of an access policy reconsiderationrequest (e.g., from a DS unit), a current access policy for the slicenames, a command, a past history of access policy reconsiderations, ahistory of slice access sequences, a request, a predetermination, a datatype, a security indicator, a priority indicator, a DSN memory systemstatus indicator, a vault utilization indicator, and a DS managing unitmessage. In an example, the processing module determines to establish anew access policy when an access policy reconsideration request isreceived from a DS unit and the history of slice access sequencesindicates a continued level of activity above a threshold. In anotherexample, the processing module determines to not establish a new accesspolicy when the access policy indicates that the slice(s) may transitionfrom available to never available and the history of slice accesssequences indicates that access activity is below a threshold. Themethod repeats to step 138 a new access policy is not going to beestablished.

When a new access policy is to be established, the method continues atstep 142 where the processing module determines the timestamp of whenthe decision was made. At step 144, the processing module determines anew access policy based on one or more of an access policyreconsideration request (e.g., from a DS unit), a current access policyfor the slice name(s), a command, a past history of access policyreconsiderations, a history of slice access sequences, a request, apredetermination, a data type, a security indicator, a priorityindicator, a DSN memory system status indicator, a vault utilizationindicator, and a DS managing unit message. In an example, the processingmodule determines the new access policy to extend the availability byone month when an access policy reconsideration request is received froma DS unit and the history of slice access sequences indicates acontinued level of activity above a threshold. In another example, theprocessing module determines the new access policy to include user ID457 to be authorized for access availability 24 hours a day for the nextfive months when a command is received from the DS managing unit. Atstep 146, the processing module sends the new access policy to the DSunits that contain the slice(s) of the slice name(s) such that the DSunits may store and utilize the new access policy.

FIGS. 10A-10C are schematic block diagrams of embodiments of a dispersedstorage network (DSN) memory storage sets. As illustrated, FIGS. 10A-Crepresent DSN memory storage sets 148-152 (e.g., the set of DS unitsthat store all the pillars of a common data segment) comprising six DSunits 1-6. For example, pillar 1 slices are stored in DS unit 1, pillar2 slices are stored in DS unit 2, pillar 3 slices are stored in DS unit3, pillar 4 slices are stored in DS unit 4, pillar 5 slices are storedin DS unit 5, pillar 6 slices are stored in DS unit 6 when theoperational parameters include a pillar width of n=6 and a readthreshold of 4. As illustrated, FIGS. 10A-C indicate slice availabilitypatterns in accordance with an access policy.

As illustrated, FIG. 10A indicates an access policy pattern from thehours of 12:00 AM to 6:00 AM, FIG. 10B illustrates an access policypattern from the hours of 6:00 AM to 7:00 PM, and FIG. 10C illustratesan access policy pattern from the hours of 7:00 PM to 12:00 AM. Notethat the access policy pattern may vary second by second, minute byminute, day by day, month-by-month, etc.

Based on these access policy patterns, DS units may read and/or writeslices in vault 1 and/or vault 2 during the specified times of day whenthe particular vault does not include an X. For example, the pillar 2for vault 1 is not available from 12:00 AM to 6:00 AM and the pillar 2for vault 2 is available from 12:00 AM to 6:00 AM as illustrated by FIG.10 A.

Note that the access policy pattern may be utilized to impact datasecurity and performance of the system. For example, the pattern mayenable all of the pillars of a vault to be available in any one or moretime frames to improve system performance. In another example, thepattern may enable just a read threshold of the pillars of a vault to beavailable in any one or more time frames to improve system security butmaintain a moderate level of system performance (e.g., as long as thoseexact pillars remain active). In another example, the pattern may neverenable a read threshold of the pillars of a vault to be available in anysingle time frame to improve system security. In that scenario thepattern may enable a read threshold of the pillars of a vault to beavailable across two or more time frames. As illustrated, vault 1 neverhas a read threshold (e.g., four pillars) number of pillars available inany one of the three time periods. For example, only pillars 4-6 areavailable for vault 1 from 12:00 AM to 6:00 AM, only pillars 1-3 areavailable for vault 1 from 6:00 AM to 7:00 PM, and only pillars 1, 5, 6are available for vault 1 from 7:00 PM to 12:00 AM. As illustrated, thedata segments may be retrieved from vault 1 by access vault 1 across twotimeframes. For example, a DS processing unit may reconstruct a vault 1data segment by retrieving slices of vault 1 from DS units 4-6 duringthe 12:00 AM-6:00 AM timeframe, followed by retrieving slices of vault 1from any one or more of DS units 1-3 during the 6:00 AM-7:00 PMtimeframe.

FIG. 11 is another flowchart illustrating another example of updating anaccess policy. The method begins with step 154 where a processing module(e.g., of one of a DS processing unit, a DS unit, a storage integrityprocessing unit, a DS managing unit and/or a user device) determines atimestamp of the current time. At step 156, the processing moduledetermines whether it is time to change an access policy (e.g., who canaccess the slice and/or when the slice can be accessed) based on one ormore of an access policy reconsideration request (e.g., from a DS unit),a current access policy, a command, a past history of access policychanges, a history of slice access sequences, a request, apredetermination, a data type, a security indicator, a priorityindicator, a DSN memory system status indicator, a vault utilizationindicator, and a DS managing unit message. In an example, the DSprocessing determines to change the access policy when an access policyreconsideration request is received from a DS unit and the history ofslice access sequences indicates a continued level of activity above athreshold. In another example, the DS processing determines to changethe access policy when the DSN memory system status indicator indicatesthat more security is desired. The method repeats to step 154 when theDS processing determines to not change the access policy.

When access policy is to be changed, the method continues at step 158where the processing module determines an access scheme of the accesspolicy where the access scheme includes one or more of a fully availablescheme (e.g., all pillars available in at least one timeframe), aminimal available scheme (e.g., just a read threshold number of pillarsare available in one or more timeframes), and a disjoint availabilityscheme (e.g., a read threshold number of pillars are available acrosstwo or more timeframes). Such a determination may be based on one ormore of an access policy reconsideration request (e.g., from a DS unit),the current access policy, a command, a past history of access policychanges, a history of slice access sequences, a request, apredetermination, a data type, a security indicator, a priorityindicator, a DSN memory system status indicator, a vault utilizationindicator, and a DS managing unit message.

In an example, the processing module determines the access scheme to befully available for the next timeframe when the performance indicatorindicates a higher level of required performance and the securityindicator indicates that a lower level of security is allowable. Inanother example, the processing module determines the access scheme tobe minimally available when the security indicator indicates a higherlevel of required security and the performance indicator indicates thata lower level of performance is allowable. In yet another example, theprocessing module determines the access scheme to be disjointavailability when the security indicator indicates a much higher levelof required security and the performance indicator indicates that a verylow level of performance is allowable.

When the access scheme is to be fully available, the method continues atstep 160 where the processing module sets the access policy as fullyavailable for at least one timeframe. Note that the access policypattern(s) may constrain availability of slices and/or vaults based on afunction of time, user ID(s), system unit ID(s), and/or other factors(e.g., security priorities, performance priorities, etc.).

At step 162, the processing module sends the access policy to DS unitsof a DS unit storage set of the slices and/or vaults of the change suchthat the DS units may store and utilize the new access policy. Note thatthe DS processing may send the access policy at the start of a newtimeframe transition or in advance of one or more timeframes where theaccess policy may include more than one access scheme of the accesspolicy.

When the access scheme is to be minimally availability, the methodcontinues at step 164 where the processing module sets the access policyas minimal availability for at least one timeframe. The method continuesat step 166 where the processing module determines a previous accesspolicy pattern (e.g., a lookup) to identify pillars that wereunavailable and pillars that were available.

The method continues at step 168, the processing module determines theaccess policy pattern based on the previous access policy pattern tochoose which pillars to make unavailable and which pillars to makeavailable such that a read threshold number of pillars is available inany one timeframe. For example, the processing module changes thepattern of vault 2 from a read threshold of four available pillars(e.g., 2, 4-6) as illustrated in the timeframe of FIG. 10 A to thepattern of vault 2 where the read threshold of four available pillars isdifferent (e.g., 1-3, 6) as illustrated in the timeframe of FIG. 10 B.The method continues at step 170 where the processing module sends theaccess policy to the DS units of a DS storage set of the slices and/orvaults of the change such that the DS units may store and utilize thenew access policy. Note that the processing module may send the accesspolicy at the start of a new timeframe transition or in advance of oneor more timeframes where the access policy may include more than oneaccess scheme of the access policy.

When the access scheme is to be disjointly availability, the methodcontinues at step 172 where the processing module sets the access policyas disjoint availability for at least one timeframe. The methodcontinues at step 174 where the processing module determines a previousaccess policy pattern (e.g., a lookup) to identify pillars that wereunavailable and pillars that were available. The method continues atstep 176 where the processing module determines the access policypattern based on the previous access policy pattern to choose whichpillars to make unavailable and which pillars to make available suchthat a read threshold of pillars is only available across twoconsecutive timeframes. For example, the processing module changes thepattern of vault 1 of only three available pillars (e.g., 1, 5, 6) asillustrated in the timeframe of FIG. 10 C to the pattern of vault 2 ofthree available pillars (e.g., 4-6) as illustrated in the timeframe ofFIG. 10 A. The processing module may recreate a data segment from slicesretrieved from the available vault 1 pillars in those two timeframes.Note that the processing module cannot recreate a data segment fromslices retrieved from the available vault 1 pillars in just one thosetwo timeframes since three pillars are available and the read thresholdis four.

The method continues at step 178 where the processing module sends theaccess policy to the DS units of a DS storage set of the slices and/orvaults of the change such that the DS units may store and utilize thenew access policy. Note that the processing module may send the accesspolicy at the start of a new timeframe transition or in advance of oneor more timeframes where the access policy may include more than oneaccess scheme of the access policy.

FIG. 12 is a flowchart illustrating an example of retrieving a dataobject. The method begins with step 180 where a processing modulereceives a data retrieval request from a requester. The data retrievalrequest may be received from any one of a user device, a DS processingunit, a storage integrity processing unit, a DS managing unit, andanother DS unit. The data retrieval request may include one or more of adata object name, a data segment identifier, a requester ID, a command,an access policy update, a data object ID, a source name, a data type, adata size indicator, a priority indicator, a security indicator, and aperformance indicator. Note that the data retrieval request may be for adata object or for one or more data segments of a data object stored asencoded data slices in a dispersed storage network (DSN) memory.

At step 182, the processing module obtains a real-time indicatorcorresponding to when the data retrieval request was received (e.g., asystem clock time). At step 184, the processing module determines atime-based data access policy based on the data retrieval request andthe real-time indicator. Such a determination may be based on one ormore of a previous time-based data access policy, a policy schedule, adata identifier, the real-time indicator, a requester identifier, a datatype, a priority indicator, a security indicator, and a dispersedstorage network (DSN) status indicator. For example, the processingmodule determines the time-based data access policy based on a storedaccess policy for the data object name. Note that the processing modulemay adjust the time-based data access policy based on priority of deviceissuing the data retrieval request. For example, the processing moduledetermines the priority of device based on a vault look up or byextracting the priority of device from the data retrieval request.Alternatively, the processing module may extract the time-based dataaccess policy from the data retrieval request when priority of deviceissuing the data retrieval request is at a first priority level (e.g., arequired predefined priority level).

At step 186, the processing module accesses a plurality of dispersedstorage (DS) units in accordance with the time-based data access policyto retrieve encoded data slices. The processing module identifies afirst set of DS units of the plurality of DS units that are accessibleduring a first time interval in accordance with the time-based dataaccess policy. In addition, or in a subsequent step, the processingmodule may identify a second set of DS units of the plurality of DSunits that are accessible during a second time interval in accordancewith the time-based data access policy. Note that the number of DS unitsin each of the first and second sets of DS units is less than thethreshold number of encoded data slices.

At step 188, the processing module sends slice retrieval messages to theDS units. In an example, the processing module sends slice retrievalmessages only to the DS units that are known to be available now (e.g.,the first set of DS units), even if the number of pillars is below theread threshold. In another example, the processing module sends sliceretrieval messages to the DS units storing the pillars of the encodeddata slices even if some of the pillars are known to be currentlyunavailable. The DS units may queue the retrieval request for subsequentprocessing when the vault becomes available in accordance with thetime-based access data policy. Alternatively, the DS units may respondwith a denial message and not queue the request.

At step 190, the processing module receives slices from the DS units. Atstep 192, the processing module determines whether a threshold number ofslices have been received (e.g., based on counting them and comparingthem to the threshold of the operational parameters). Note that theprocessing module may send an error message to the DS managing unit whena slice is not received within a receive time period from a DS unit thatwas sent a retrieval request.

When at least a threshold number of slices have been received, themethod continues at step 194 where the processing module decodes thethreshold number of encoded data slices in accordance with an errorcoding dispersal storage function when a threshold number of the encodeddata slices have been retrieved. The processing module aggregates allthe data segments to recreate the data object when the processing moduleretrieves more than one data segment. The processing module sends thedata to the requester.

The method continues at step 196 where the processing module generates aretrieval status message in accordance with the time-based data accesspolicy when the threshold number of the encoded data slices has not beenretrieved. The retrieval status message may include one or more of thedata object name, the data segment ID, an indicator of the amount of thedata object retrieved so far, an indicator of the amount of the dataobject pending retrieval, and an estimated timeframe of when the dataobject will be fully retrieved. For example, the processing module sendsthe retrieval status message to the requester. In another example, theprocessing module sends the retrieval status message to the requesterfor each time the method passed through this step (e.g., each time theprocessing module waits to retrieve another group of slices).

The method continues at step 198 wherein the processing moduledetermines whether it is time to continue to retrieve slices based onone or more of the time-based data access policy, an access policypattern, which pillars have been tried so far, which pillars are stillrequired, and the current real-time indicator. For example, theprocessing module determines that it is not time to continue to retrieveslices when no access policy pattern transitions have occurred and morepillars are required (e.g., no new pillars are available yet). Themethod repeats at step 198 when it is not time to continue to retrieveslices and branches to step 186 when it is time to continue retrievingslices (e.g., try new pillars when a timeframe transition has occurredmaking more pillars available).

In a data storage example of operation, a processing module receives adata write request from a requesting device, wherein the data writerequest includes data. The processing module encodes the data into a setof encoded data slices in accordance with an error coding dispersalstorage function. Next, the processing module identifies a set ofdispersed storage (DS) units and a time-based data access policy basedon a privilege set of the requesting device. For example, the processingmodule identifies the set of DS units based on the privilege set of therequesting device and generates the time-based data access policy basedon the set of DS units. In another example, the processing moduleidentifies the time-based data access policy based on the privilege setof the requesting device and generates the set of DS units based on thetime-based data access policy. As yet another example, the processingmodule identifies the set of DS units and the time-based data accesspolicy by obtaining a real-time indicator corresponding to when the datawrite request was received and identifying the set of DS units and thetime-based data access policy based on the real-time indicator. As afurther example, the processing module identifies the set of DS unitsand the time-based data access policy by extracting the identifying theset of DS units and the time-based data access policy from the datawrite request when priority of the requesting device is at a firstpriority level. After identifying the DS units, the processing moduleoutputs the set of encoded data slices to the set of DS units inaccordance with the time-based data access policy.

FIG. 13 is a schematic block diagram of another embodiment of acomputing system that includes a DS processing unit A, a plurality of DSunits 1-4, and a DS processing unit B. Each of DS processing units A andB may be coupled to the plurality of DS units 1-4 via the networkresulting in unique time delay values between DS processing units Aand/or B and the plurality of DS units 1-4.

In an example of data storage, DS processing unit A encodes a datasegment (e.g., a portion of data) in accordance with an error codingdispersed storage function to produce a pillar 1 slice, a pillar 2slice, a pillar 3 slice, and a pillar 4 slice. DS processing unit Adetermines time delays to send information to each of the plurality ofDS units 1-4 based on one or more of a real time query (e.g., a ping), alookup, a message, a vault value, a command, a message from the DSmanaging unit, and a predetermination. For example the DS processingunit A determines a first time delay between itself and DS unit 1 (tdA1), a second time delay between itself and DS unit 2 (td A2), a thirdtime delay between itself and DS unit 3 (td A3), and a fourth time delaybetween itself and DS unit 4 (td A4).

The DS processing unit A then determines the DS having the longest timedelay (td long) and determines an availability delay (ad) number foreach of the DS units based on the longest time delay and a time delay ofa path to the DS unit as: ad=td long−td. For example, the availabilitydelay for the path from the DS processing unit A to the DS unit 1 isavailability delay A1 (ad A1). Note that the availability delay for thepath with the longest delay is 0.

In another example of operation, DS processing unit A determines a readthreshold number of DS units of the plurality of DS units that haveshortest time delays. Next, DS processing unit A determines a DS unitwith the longest time delay (td long) of a subset of DS units that weredetermined to have the shortest time delays. The DS processing unit Adetermines an availability delay (ad) number for each DS unit of asubset of DS units that were determined to have the shortest time delaysbased on the longest time delay value and the time delay of the path tothe DS unit as: ad=td long−td. The DS processing unit A determines theavailability delay to be zero for remaining DS units outside of thesubset of DS units that were determined to have the shortest timedelays. For example, the availability delay for the path from the DSprocessing unit A to the DS unit 3 is availability delay A3 (ad A3).Note that the availability delay for the path of the subset with thelongest delay is 0.

Next, the DS processing unit A sends each pillar slice and correspondingavailability delay to the corresponding DS unit at substantially thesame time. For example, DS processing unit A sends pillar 1 slice and adA1 to DS unit 1, DS processing unit A sends pillar 2 slice and ad A2 toDS unit 2, DS processing unit A sends pillar 3 slice and ad A3 to DSunit 3, and DS processing unit A sends pillar 4 slice and ad A4 to DSunit 4. The DS unit receives the pillar slice and correspondingavailability delay from DS processing unit A. The DS unit stores theslice in memory and establishes a slice status as unavailable and/orpending availability (e.g., marks a table in memory that the slice isnot retrieval yet). Note that any retrieval attempts at this moment willnot result in the immediate slice retrieval. The DS unit starts a timerwith the value of the availability delay. The DS unit changes the slicestatus to available such that the slice may be successfully retrievedwhen the timer has expired. For example, DS unit 2 receives pillar 2slice and availability delay ad A2 from DS processing unit A. DS unit 2stores the pillar 2 slice, marks the status as unavailable, and starts atimer with the value ad A2. DS unit 2 changes the pillar 2 slice statusto available when the timer expires. The DS unit 2 may retrieve thepillar 2 slice based on a retrieval request.

The slices of all of the pillars become available as a function of thedelays. In an instance, the slices of all of the pillars becomeavailable at substantially the same time. In another instance, a readthreshold slices of the DS units with the shortest time delays becomeavailable at substantially the same time. An example timing diagram isdiscussed with reference to FIG. 14.

In another example of operation, the method enables retrieved slicesfrom the plurality of DS units to arrive substantially at the same timeat DS processing unit B in response to a retrieval request from DSprocessing unit B. DS processing unit B determines time delays toretrieve information between the each of the plurality of DS units 1-4and DS processing unit B. DS processing unit B and the plurality of DSunits 1-4 may be operably coupled via the network resulting in uniquetime delay values between the plurality of DS units 1-4 and DSprocessing unit B. The time delay determination may be based on one ormore of a real time query (e.g., a ping), a lookup, a message, a vaultvalue, a command, a message from the DS managing unit, and apredetermination. The DS processing unit B determines a time delaybetween the DS unit 1 and DS processing unit B as time delay B1 (td B1),a time delay between the DS unit 2 and DS processing unit B as timedelay B2 (td B2), a time delay between the DS unit 3 and DS processingunit B as time delay B3 (td B3), and a time delay between the DS unit 4and DS processing unit B as time delay B4 (td B4).

In an example, DS processing unit B determines a DS unit of theplurality of DS units with a longest time delay (td long). The DSprocessing unit B determines a send delay (sd) number for each DS unitbased on the longest time delay and the time delay of the path from theDS unit as: sd=td long−td. For example, the send delay for the path fromthe DS unit 1 to DS processing unit B is send delay B1 (sd B1). Notethat the send delay for the path with the longest delay is 0. In anotherinstance, the DS processing B may determine each send delay as sd=2*tdlong−2*td to account for the delay in sending the retrieval request tothe DS unit.

In another example, DS processing unit B determines a read thresholdnumber of DS units of the plurality of DS units that have the shortesttime delays. Next, DS processing unit B determines a DS unit with thelongest time delay (td long) of a subset of DS units that weredetermined to have the shortest time delays. The DS processing unit Bdetermines a send delay (sd) number for each DS unit of the subset of DSunits that were determined to have the shortest time delays based on thelongest time delay value and the time delay of the path from the DS unitas: sd=td long−td. The DS processing unit B determines the send delay tobe zero for the remaining DS units outside of the subset of DS unitsthat were determined to have the shortest time delays. For example, thesend delay for the path from the DS unit 3 to the DS processing unit Bis send delay B3 (sd B3). Note that the availability delay for the pathof the subset with the longest delay is 0. In another instance, the DSprocessing B may determine each send delay as sd=2*td long−2*td toaccount for the delay in sending the retrieval request to the DS unit.

In the next step, the DS processing unit B sends each DS unit aretrieval request for the pillar slices and corresponding send delay atsubstantially the same time. For example, DS processing unit B sends aretrieval request for pillar 1 slice and sd B1 to DS unit 1, DSprocessing unit B sends a retrieval request for pillar 2 slice and sd B2to DS unit 2, DS processing unit B sends a retrieval request for pillar3 slice and sd B3 to DS unit 3, and DS processing unit B sends aretrieval request for pillar 4 slice and sd B4 to DS unit 4.

The DS unit receives the pillar slice retrieval request andcorresponding send delay from DS processing unit B. The DS unit starts atimer with the value of the send delay. The DS unit may retrieve thepillar slice from memory and cache it. The DS unit sends the pillarslice from the cache to DS processing unit B when the timer has expired.For example, DS unit 2 receives a pillar 2 slice retrieval request andsend delay sd B2 from DS processing unit B. DS unit 2 starts a timerwith the value sd B2. DS unit 2 retrieves the pillar 2 slice and sendsit to DS processing unit B when the timer expires.

Note that in an example of operation slices of all of the pillars arriveat the requesting DS processing unit B at substantially the same time.In another example, a read threshold slices of the DS units with theshortest time delays arrive at the requesting DS processing unit B atsubstantially the same time. Note that uniform availability ofdistributedly stored information may be desirable when the informationis of a time sensitive nature such as financial transactions (e.g.,market arbitrage). An example timing diagram is discussed with referenceto FIG. 15.

FIG. 14 is a timing diagram of an example storage sequence. Asillustrated, the left edge of the timing diagram illustrates the timewhen the plurality of slices are sent from the dispersed storage (DS)processing at substantially the same time (e.g., t=send from DSprocessing unit A). The time delays from the DS processing unit to eachDS unit of a plurality of DS units is illustrated by td A1, td A2, tdA3, and td A4. The DS units receive the slice at the end of the timedelay and start the availability delay timers ad A1, ad A2, ad A3, andad A4. Note that the availability delay for the third path ad A3=0 sincetd A3 is the longest of the time delay values. The DS units change theslice status to available at substantially the same time when the timersexpire (e.g., t=available at DS units).

FIG. 15 is a timing diagram of an example retrieval sequence. Asillustrated, the left edge of the timing diagram illustrates the timewhen the plurality of dispersed storage (DS) units start a unique senddelay timer sd B1, sd B2, sd B3, and sd B4 upon receiving a retrievalrequest (e.g., t=start at DS units). Note that the send delay for thefourth path sd B4=0 since td B4 is the longest of the time delay values.The DS units send their slice to the DS processing unit B when the timerexpires. Note that the slices are sent from the DS units at differenttimes. The time delays from each of the DS units to the DS processingunit B is illustrated by td B1, td B2, td B3, and td B4. The slicesarrive at the DS processing unit B at substantially the same time (e.g.,t=arrive at DS processing unit B).

FIG. 16 is a flowchart illustrating an example of storing a data object.The method begins with step 200 where a processing module receives astore request and a data object to store from any one of a user device,a DS processing unit, a storage integrity processing unit, a DS managingunit, and another DS unit. The request may include a command, a user ID,a data object name, a data type, a data size, a priority indicator, asecurity indicator, a performance indicator, operational parameters,time delay to DS units information, and other metadata pertaining to thedata object.

At step 202, the processing module determines operational parameters anda plurality of DS units of a DSN memory storage set based on one or moreof vault information, a predetermination, a command, the user ID, thedata object name, the data type, the data size, the priority indicator,the security indicator, the performance indicator, the time delay to DSunits information, and the other metadata.

At step 204, the processing module determines time delays to sendinformation between the DS processing and each of the plurality of DSunits. Such a determination may be based on one or more of a real timequery (e.g., a ping), a lookup, a message, a vault value, a command, amessage from the DS managing unit, and a predetermination. At step 206,the DS processing determines availability delays for each DS processingof the plurality of DS units. Such a determination may be based on oneor more of the time delays, the operational parameters, a message, avault value, a command, a message from the DS managing unit, and apredetermination. In an example, the processing module determines theavailability delay based on a DS unit with a longest time delay aspreviously discussed. In another example, the processing moduledetermines the availability delay based on a DS unit with a longest timedelay of a read threshold subset of the plurality of DS units withshortest time delays as previously discussed.

At step 208, the processing module encodes the data object utilizing anerror coded dispersal stored function and in accordance with theoperational parameters to produce encoded data slices. The processingmodule then sends the encoded data slices and corresponding availabilitydelays to the plurality of DS units at substantially the same time.

FIG. 17 is another flowchart illustrating another example of retrievingencoded data slices. The method begins at step 212 where a processingmodule (e.g., of a DS unit) receives a slice retrieval request from arequester (e.g., any one of a user device, a DS processing unit, astorage integrity processing unit, a DS managing unit, and a DS unit) toretrieve a slice. The request may include one or more of slice name(s),a requester ID, a command, an access policy update, a send delay, a dataobject ID, a source name, a data type, a data size indicator, a priorityindicator, a security indicator, and a performance indicator.

At step 214, the processing module determines an access policy to applyto the retrieval request based on one or more of a lookup in memory ofpreviously received access policy, the slice name(s), the requester ID,a command, an access policy update, a data object ID, a source name, adata type, a data size indicator, a priority indicator, a securityindicator, and a performance indicator. For example, the processingmodule determines the access policy based on the stored access policyfor the slice names. At step 216, the processing module determines atimestamp.

At step 218, the processing module retrieves the slice from memory. Atstep 220, the processing module determines a send delay based on one ormore of a send delay received with the slice retrieval request, a query,the access policy, the timestamp, a memory status indicator, a DS unitstatus indicator, and a performance indicator. In an example, theprocessing module utilizes the received send delay value as the senddelay. In another example, the processing module queries each of theother DS units of the storage set to determine the time delay from eachof the other DS units to retrieval requester. The processing moduledetermines the send delay based on the determined time delays aspreviously discussed.

At step 222, the processing module starts a timer based on the value ofthe send delay. The processing module determines whether it is time tosend the slice to the requester based of the timer (e.g., the timerexpires). When it is time to send, the method continues at step 226where the processing module sends the retrieved slice to the requestersuch that a plurality of slices from a DS unit associated with theprocessing module and other DS units of a same DS unit storage set(e.g., the other pillars) for the same data segment substantially arriveat the requester at the same time.

FIG. 18 is a schematic block diagram of another embodiment of acomputing system that includes a DS processing unit A, a DS processingunit B, and a plurality of DS units 1-4. In such a system, two or moreDS processing units send EC data slices of two or more data objects tothe same set of DS units such that the data objects are substantiallyreceived by the DS units at the same time. Note that uniformavailability of distributedly stored information may be desirable whenthe information is of a time sensitive nature such as financialtransactions (e.g., market arbitrage). For example, two or more DSprocessing units may place market orders with a clearing house bysending the orders to the same clearing house such that the ordersarrive at substantially the same time.

In an example of operation, DS processing unit A encodes a data segmentutilizing an error coded dispersal storage function to produce a pillar1 slice, a pillar 2 slice, a pillar 3 slice, and a pillar 4 slice. DSprocessing unit A determines time delays to send information between DSprocessing unit A and each of the plurality of DS units 1-4. DSprocessing unit A and the plurality of DS units 1-4 may be operablycoupled via a network resulting in unique time delay values between DSprocessing unit A and the plurality of DS units 1-4. The time delaydetermination may be based on one or more of a real time query (e.g., aping), a lookup, a message, a vault value, a command, a message from theDS managing unit, and/or a predetermination. The DS processing unit Adetermines a time delay between the DS processing unit A and DS unit 1as time delay A1 (td A1), a time delay between the DS processing unit Aand DS unit 2 as time delay A2 (td A2), a time delay between the DSprocessing unit A and DS unit 3 as time delay A3 (td A3), and a timedelay between the DS processing unit A and DS unit 4 as time delay A4(td A4).

DS processing unit B encodes a data segment in accordance with the errorcoded dispersal stored function to produce a pillar 1 slice, a pillar 2slice, a pillar 3 slice, and a pillar 4 slice. DS processing unit Bdetermines time delays to send information between DS processing unit Band each of the plurality of DS units 1-4. DS processing unit B and theplurality of DS units 1-4 may be operably coupled via the networkresulting in unique time delay values between DS processing unit B andthe plurality of DS units 1-4. The time delay determination may be basedon one or more of a real time query (e.g., a ping), a lookup, a message,a vault value, a command, a message from the DS managing unit, and apredetermination. The DS processing unit B determines a time delaybetween the DS processing unit B and DS unit 1 as time delay B1 (td B1),a time delay between the DS processing unit B and DS unit 2 as timedelay B2 (td B2), a time delay between the DS processing unit B and DSunit 3 as time delay B3 (td B3), and a time delay between the DSprocessing unit B and DS unit 4 as time delay B4 (td B4).

The DS processing unit A and DS processing unit B share time delayinformation such that DS processing unit A determines td B1, td B2, td,B3, and td B4 and DS processing unit B determines td A1, td A2, td, A3,and td A4. In an example, the DS processing units A and B share the timedelay information via a link between them. In another example, the DSprocessing units A and B share the time delay information via passingthe time delay information through one or more of the DS units 1-4.

In an example of operation, the DS processing unit A and/or B determinesthe DS unit and path of the plurality of DS unit 1-4 with a longest timedelay (td long) of all the time delays td A1−td A4 and td B1−td B4. TheDS processing unit A and/or B determines a send delay (sd) number foreach DS processing A and B to each DS unit based on the longest timedelay and the time delay of the path to the DS unit as: sd=td long−td.For example, the send delay for the path from the DS processing unit Bto the DS unit 1 is send delay B1 (sd B1). Note that the send delay forthe one path of eight with the longest delay is 0.

In another example, the DS processing unit A and/or B determines a readthreshold number of DS units from the perspective of each of the DSprocessing units A and B of the plurality of the DS units that haveshortest time delays (e.g., two paths). Next, the DS processing unit Aand/or B determines the DS unit path with the longest time delay (tdlong) of a subset of DS units that were determined to have the shortesttime delays. The DS processing unit A and/or B determines a send delay(sd) number for each DS unit of the subset of DS units that weredetermined to have the shortest time delays based on the longest timedelay value and the time delay of the path to the DS unit as: sd=tdlong−td. The DS processing unit A and/or B determines the send delay tobe zero for the remaining DS units outside of the subset of DS unitsthat were determined to have the shortest time delays. For example, thesend delay for the path from the DS processing unit A to the DS unit 3is send delay A3 (sd A3). Note that the send delay for the path of thesubset with the longest delay is 0.

In the next step, the DS processing units A and B start send delaytimers for each of the values of the determined sends delays atsubstantially the same time. The DS processing units A and B send slicesfor a pillar to the DS unit when the corresponding send timer expires.For example, DS processing unit A sends pillar 1 slice to DS unit 1 whensend timer sd A1 expires. In another example, DS processing unit B sendspillar 3 slice to DS unit 3 when send timer sd B3 expires, etc.

The DS unit receives the pillar slice from DS processing unit A and Bsuch that the data objects sent from DS processing units A and B arestored in the DS units substantially at the same time. Note that in anembodiment the slices of all of the pillars from both DS processingunits A and B become available at substantially the same time. Inanother embodiment a read threshold slices for both data objects of theDS units with the shortest time delays become available at substantiallythe same time. An example timing diagram is discussed with reference toFIG. 19.

FIG. 19 is another timing diagram of another example storage sequence.As illustrated, the timing diagram illustrates the timing of twodispersed storage (DS) processing units storing slices to a plurality ofcommon DS units where the slices from the two DS processing units arriveat the common DS units at substantially the same time.

As illustrated, the left edge of the timing diagram illustrates the timewhen the DS processing units A and B start a unique send delay timer sdA1, sd A2, sd A3, sd A4, sd B1, sd B2, sd B3, and sd B4 upon starting acoordinated store sequence (e.g., t=send from DS processing units A andB). Note that the send delay for the third path sd A3=0 since td A3 isthe longest of the time delay values. The DS processing units A and Bsend their slice to the DS units when each of the send timers expires.Note that the slices are sent from the DS processing units at differenttimes. The time delays from the DS processing units A and B to each ofthe DS units 1-4 is illustrated by td A1, td A2, td A3, td A4, td B1, tdB2, td B3, and td B4. The slices arrive at the common DS units atsubstantially the same time (e.g., t=arrive at DS units).

FIG. 20 is a flowchart illustrating an example of outputting slices. Themethod begins with step 228 where a processing module receives a storerequest and a data object to store from any one of a user device, a DSprocessing unit, a storage integrity processing unit, a DS managingunit, and another DS unit. The request may include a command, a user ID,a data object name, a data type, a data size, a priority indicator, asecurity indicator, a performance indicator, operational parameters,time delay to DS units information, and/or other metadata pertaining tothe data object.

At step 230, the processing module determines operational parameters anda plurality of DS units of a DSN memory storage set based on one or moreof vault information, a predetermination, a command, the user ID, thedata object name, the data type, the data size, the priority indicator,the security indicator, the performance indicator, the time delay to DSunits information, and the other metadata.

At step 232, the processing module determines other potential DSprocessing sources that may send slices to the same common set of DSunits in accordance with a time-coordinated approach based on one ormore of a query, a schedule, vault information, a predetermination, acommand, the user ID, the data object name, the data type, the datasize, the priority indicator, the security indicator, the performanceindicator, the time delay to DS units information, and the othermetadata. For example, a processing module of a DS processing unit A maydetermine that a DS processing unit B is another DS processing source byquerying DS processing unit B and receives an affirmative queryresponse.

At step 234, the processing module determines time delays to sendcfinformation between the DS processing and each of the plurality of DSunits. Such a determination may be based on one or more of a real timequery of the plurality of DS units (e.g., a ping), a query of the otherDS processing source(s), shared information between DS processing units,a lookup, a message, a vault value, a command, a message from the DSmanaging unit, and a predetermination.

At step 236, the processing module determines “send-delays” for each DSunit of the plurality of DS units. Such a determination may be based onone or more of the time delays, the operational parameters, a message, avault value, a command, a message from the DS managing unit, and apredetermination. In an example, the DS processing unit determines thesend-delay based on a DS unit with a longest time delay as previouslydiscussed. In another example, the DS processing unit determines thesend-delay based on a DS unit with a longest time delay of a readthreshold subset (e.g., including all DS unit storage sets from the DSprocessing sources) of the plurality of DS units with the shortest timedelays as previously discussed.

At step 238, the processing module encodes the data object utilizing anerror coding dispersal storage function to produce encoded data slicesfor each pillar. The DS processing starts a timer for each DS unit pathbased on the value of the send delay. At step 240, the processing moduledetermines whether it is time to send the slice to the DS unit based onthe timer. For example, the processing module determines that it is timeto send when the timer expires. The method repeats at step 240 when theDS processing determines that it is not time to send.

When it is time to send, the method continues at step 242 where theprocessing module sends the pillar slices in accordance with the timerexpiration to the corresponding DS unit. At step 244, the processingmodule determines whether slices of all the pillars have been sent tothe DS units based on which pillars of encoded data slices were createdand which pillars of encoded data slices have been sent so far. Notethat the created pillars may be less than the pillar width n. The methodrepeats at step 240 when all the pillars have not been sent and endswhen they have been.

As may be used herein, the terms “substantially” and “approximately”provides an industry-accepted tolerance for its corresponding termand/or relativity between items. Such an industry-accepted toleranceranges from less than one percent to fifty percent and corresponds to,but is not limited to, component values, integrated circuit processvariations, temperature variations, rise and fall times, and/or thermalnoise. Such relativity between items ranges from a difference of a fewpercent to magnitude differences. As may also be used herein, theterm(s) “operably coupled to”, “coupled to”, and/or “coupling” includesdirect coupling between items and/or indirect coupling between items viaan intervening item (e.g., an item includes, but is not limited to, acomponent, an element, a circuit, and/or a module) where, for indirectcoupling, the intervening item does not modify the information of asignal but may adjust its current level, voltage level, and/or powerlevel. As may further be used herein, inferred coupling (i.e., where oneelement is coupled to another element by inference) includes direct andindirect coupling between two items in the same manner as “coupled to”.As may even further be used herein, the term “operable to” or “operablycoupled to” indicates that an item includes one or more of powerconnections, input(s), output(s), etc., to perform, when activated, oneor more its corresponding functions and may further include inferredcoupling to one or more other items. As may still further be usedherein, the term “associated with”, includes direct and/or indirectcoupling of separate items and/or one item being embedded within anotheritem. As may be used herein, the term “compares favorably”, indicatesthat a comparison between two or more items, signals, etc., provides adesired relationship. For example, when the desired relationship is thatsignal 1 has a greater magnitude than signal 2, a favorable comparisonmay be achieved when the magnitude of signal 1 is greater than that ofsignal 2 or when the magnitude of signal 2 is less than that of signal1.

While the transistors in the above described figure(s) is/are shown asfield effect transistors (FETs), as one of ordinary skill in the artwill appreciate, the transistors may be implemented using any type oftransistor structure including, but not limited to, bipolar, metal oxidesemiconductor field effect transistors (MOSFET), N-well transistors,P-well transistors, enhancement mode, depletion mode, and zero voltagethreshold (VT) transistors.

The present invention has also been described above with the aid ofmethod steps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claimed invention.

The present invention has been described, at least in part, in terms ofone or more embodiments. An embodiment of the present invention is usedherein to illustrate the present invention, an aspect thereof, a featurethereof, a concept thereof, and/or an example thereof. A physicalembodiment of an apparatus, an article of manufacture, a machine, and/orof a process that embodies the present invention may include one or moreof the aspects, features, concepts, examples, etc. described withreference to one or more of the embodiments discussed herein.

The present invention has been described above with the aid offunctional building blocks illustrating the performance of certainsignificant functions. The boundaries of these functional buildingblocks have been arbitrarily defined for convenience of description.Alternate boundaries could be defined as long as the certain significantfunctions are appropriately performed. Similarly, flow diagram blocksmay also have been arbitrarily defined herein to illustrate certainsignificant functionality. To the extent used, the flow diagram blockboundaries and sequence could have been defined otherwise and stillperform the certain significant functionality. Such alternatedefinitions of both functional building blocks and flow diagram blocksand sequences are thus within the scope and spirit of the claimedinvention. One of average skill in the art will also recognize that thefunctional building blocks, and other illustrative blocks, modules andcomponents herein, can be implemented as illustrated or by discretecomponents, application specific integrated circuits, processorsexecuting appropriate software and the like or any combination thereof.

1. A method comprises: receiving a data retrieval request; obtaining areal-time indicator corresponding to when the data retrieval request wasreceived; determining a time-based data access policy based on the dataretrieval request and the real-time indicator; accessing a plurality ofdispersed storage (DS) units in accordance with the time-based dataaccess policy to retrieve encoded data slices; and when a thresholdnumber of the encoded data slices have been retrieved, decoding thethreshold number of encoded data slices in accordance with an errorcoding dispersal storage function.
 2. The method of claim 1, wherein theaccessing the plurality of dispersed storage (DS) units comprises:identifying a first set of DS units of the plurality of DS units thatare accessible during a first time interval in accordance with thetime-based data access policy; and identifying a second set of DS unitsof the plurality of DS units that are accessible during a second timeinterval in accordance with the time-based data access policy, wherein anumber DS units in each of the first and second sets of DS units is lessthan the threshold number of encoded data slices.
 3. The method of claim1 further comprises: when the threshold number of the encoded dataslices have not been retrieved, generating a retrieval status message inaccordance with the time-based data access policy.
 4. The method ofclaim 1, wherein the determining the time-based data access policy isbased on one or more of: a previous time-based data access policy; apolicy schedule; a data identifier; the real-time indicator; a requesteridentifier; a data type; a priority indicator; a security indicator; anda dispersed storage network (DSN) status indicator.
 5. The method ofclaim 1, wherein the determining the data access policy furthercomprises: adjusting the time-based data access policy based on priorityof a device issuing the data retrieval request.
 6. The method of claim1, wherein the determining the time-based data access policy comprises:extracting the time-based data access policy from the data retrievalrequest when priority of a device issuing the data retrieval request isat a first priority level.
 7. A method comprises: receiving a data writerequest from a requesting device, wherein the data write requestincludes data; encoding at least a portion of the data into a set ofencoded data slices in accordance with an error coding dispersal storagefunction; identifying a set of dispersed storage (DS) units and atime-based data access policy based on a privilege set of the requestingdevice; and outputting the set of encoded data slices to the set of DSunits in accordance with the time-based data access policy.
 8. Themethod of claim 7 further comprises: identifying the set of DS unitsbased on the privilege set of the requesting device; and generating thetime-based data access policy based on the set of DS units.
 9. Themethod of claim 7 further comprises: identifying the time-based dataaccess policy based on the privilege set of the requesting device; andgenerating the set of DS units based on the time-based data accesspolicy.
 10. The method of claim 7, wherein the identifying the set of DSunits and the time-based data access policy comprises: obtaining areal-time indicator corresponding to when the data write request wasreceived; and identifying the set of DS units and the time-based dataaccess policy based on the real-time indicator.
 11. The method of claim7, wherein the identifying the set of DS units and the time-based dataaccess policy comprises: extracting the identifying the set of DS unitsand the time-based data access policy from the data write request whenpriority of the requesting device is at a first priority level.
 12. Acomputer comprises: an interface; and a processing module operable to:receive, via the interface, a data retrieval request; each obtain areal-time indicator corresponding to when the data retrieval request wasreceived; determine a time-based data access policy based on the dataretrieval request and the real-time indicator; access, via theinterface, a plurality of dispersed storage (DS) units in accordancewith the time-based data access policy to retrieve encoded data slices;and decode the threshold number of encoded data slices in accordancewith an error coding dispersal storage function when a threshold numberof the encoded data slices have been retrieved.
 13. The computer ofclaim 12, wherein the processing module further functions to access theplurality of dispersed storage (DS) units by: identifying a first set ofDS units of the plurality of DS units that are accessible during a firsttime interval in accordance with the time-based data access policy; andidentifying a second set of DS units of the plurality of DS units thatare accessible during a second time interval in accordance with thetime-based data access policy, wherein a number DS units in each of thefirst and second sets of DS units is less than the threshold number ofencoded data slices.
 14. The computer of claim 12, wherein theprocessing module further functions to: generate a retrieval statusmessage in accordance with the time-based data access policy when thethreshold number of the encoded data slices have not been retrieved. 15.The computer of claim 12, wherein the processing module furtherfunctions to determine the time-based data access policy based on one ormore of: a previous time-based data access policy; a policy schedule; adata identifier; the real-time indicator; a requester identifier; a datatype; a priority indicator; a security indicator; and a dispersedstorage network (DSN) status indicator.
 16. The computer of claim 12,wherein the processing module further functions to determine the dataaccess policy by: adjusting the time-based data access policy based onpriority of device issuing the data retrieval request.
 17. The computerof claim 12, wherein the processing module further functions todetermine the time-based data access policy by: extracting thetime-based data access policy from the data retrieval request whenpriority of device issuing the data retrieval request is at a firstpriority level.
 18. A computer comprises: an interface; and a processingmodule operable to: receive, via the interface, a data write requestfrom a requesting device, wherein the data write request includes data;encode at least a portion of the data into a set of encoded data slicesin accordance with an error coding dispersal storage function; identifya set of dispersed storage (DS) units and a time-based data accesspolicy based on a privilege set of the requesting device; and output,via the interface, the set of encoded data slices to the set of DS unitsin accordance with the time-based data access policy.
 19. The computerof claim 18, wherein the processing module further functions to:identify the set of DS units based on the privilege set of therequesting device; and generate the time-based data access policy basedon the set of DS units.
 20. The computer of claim 18, wherein theprocessing module further functions to: identify the time-based dataaccess policy based on the privilege set of the requesting device; andgenerate the set of DS units based on the time-based data access policy.21. The computer of claim 18, wherein the processing module furtherfunctions to identify the set of DS units and the time-based data accesspolicy by: obtaining a real-time indicator corresponding to when thedata write request was received; and identifying the set of DS units andthe time-based data access policy based on the real-time indicator. 22.The computer of claim 18, wherein the processing module furtherfunctions to identify the set of DS units and the time-based data accesspolicy by: extracting the identifying the set of DS units and thetime-based data access policy from the data write request when priorityof the requesting device is at a first priority level.